Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixing remote REST QPU observe for single spin operator #2417

Merged
merged 5 commits into from
Nov 28, 2024

Conversation

bmhowe23
Copy link
Collaborator

Resolves #2382

Copy link
Collaborator

@khalatepradnya khalatepradnya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks, Ben!

@bmhowe23 bmhowe23 enabled auto-merge (squash) November 28, 2024 05:27
@bmhowe23 bmhowe23 merged commit c9d0e4c into NVIDIA:main Nov 28, 2024
213 checks passed
@bettinaheim bettinaheim added the bug fix To be listed under Bug Fixes in the release notes label Dec 10, 2024
@bettinaheim bettinaheim added this to the release 0.9.1 milestone Dec 10, 2024
@bettinaheim bettinaheim changed the title Follow-up to #2394 - handle remote REST QPU also Fixing remote REST QPU observe for single spin operator Dec 10, 2024
@bettinaheim bettinaheim added the no release notes Don't list this PR in the release notes label Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug fix To be listed under Bug Fixes in the release notes no release notes Don't list this PR in the release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Hardware path] cudaq.observe() incorrectly returns 0.0 when there is only a single spin op term
4 participants